Optimal array addressing control structure comprising an I-frame only video encoder and a frame difference unit which includes an address counter for addressing memory addresses

ABSTRACT

A scalable architecture MPEG2 compliant digital video encoder system having an I-frame video encoder module with a Discrete Cosine Transform processor, a quantization unit, a variable length encoder, a FIFO buffer, and a compressed store interface, for generating an I-frame containing bitstream. The system also includes a second processor element with a reference memory interface, motion estimation and compensation capability, inverse quantization, and inverse discrete cosine transformation, and motion compensation means; and at least one third processor element for motion estimation. According to the invention, the difference data between the current macroblock and the reference macroblock is stored, which may be of different formats, is storted in memory in a common format by blocking bits in an address counter of the memory.

FIELD OF THE INVENTION

The invention relates to apparatus for encoding digital visual images, including spatial (intra-picture) and temporal (inter-picture) compression, that is reducing both redundancy within a picture and redundancy between pictures. Redundancy within pictures is reduced, or even eliminated, by the use of the discrete cosine transform, quantization, and variable length encoding. Redundancy between pictures is reduced, or even eliminated, through the use of motion vectors. One aspect of temporal compression, that is, compression between pictures, is calculating the difference between the current macroblock and the reference macroblock. This difference is calculated in a frame difference unit. The frame difference unit receives macroblock data in various formats and, by blocking bits in an address counter, stores the macroblock data in a memory in a common format.

BACKGROUND OF THE INVENTION

Within the past decade, the advent of world-wide electronic communications systems has enhanced the way in which people can send and receive information. In particular, the capabilities of real-time video and audio systems have greatly improved in recent years. In order to provide services such as video-on-demand and videoconferencing to subscribers, an enormous amount of network bandwidth is required. In fact, network bandwidth is often the main inhibitor to the effectiveness of such systems.

In order to overcome the constraints imposed by networks, compression systems have emerged. These systems reduce the amount of video and audio data which must be transmitted by removing redundancy in the picture sequence. At the receiving end, the picture sequence is uncompressed and may be displayed in real-time.

One example of an emerging video compression standard is the Moving Picture Experts Group ("MPEG") standard. Within the MPEG standard, video compression is defined both within a given picture and between pictures. Video compression within a picture is accomplished by conversion of the digital image from the time domain to the frequency domain by a discrete cosine transform, quantization, variable length coding, and Huffman coding. Video compression between pictures is accomplished via a process referred to as motion estimation, in which a motion vector plus difference data is used to describe the translation of a set of picture elements (pels) from one picture to another.

The ISO MPEG2 standard specifies only the syntax of bitstream and semantics of the decoding process. The choice of coding parameters and trade-offs in performance versus complexity is left to the encoder developers.

One aspect of the MPEG2 compliant encoding process is calculating the difference between the current and reference macroblocks. This is accomplished in a Frame Difference Unit (FD). Because of specific macroblock encoding algorithms, data to be processed through the frame difference unit arrives in various word lengths and must be formatted such that when used it has the same format as other data. The Frame Difference Unit calculates the difference, that is the difference in luminance and chrominance, between the current macroblock and the best match reference macroblock. Data, that is reference macroblock chrominance and luminance data and current macroblock chrominance and luminance data, to be processed through the Frame Difference Unit arrives in various word lengths and must be formatted such that when used it has the same format as other source data that is used. Data may be stored to and retrieved from memory in two different orders, depending on controls within the Frame Difference Unit. The data also needs to be reformatted prior to sending it to the next unit in the Encoder. These various word lengths and formatting requirements impose difficulties in designing storage arrays within the Frame Difference Unit.

Thus a need exists for formatting macroblock data. Furthermore data must be stored to and retrieved from memory in two different orders. A need exists for a Frame Difference unit capable of storing and retrieving data in different orders. Thus a need exists for frame difference unit storage arrays capable of storing and delivering data in different orders. Finally, the data also needs to be reformatted prior to sending it to the next unit in the encoder. A need exists for reformatting the data prior to sending it to the next unit in the encoder.

OBJECTS OF THE INVENTION

It is a primary objective of the invention to provide a system and method for formatting reference and current macroblock data prior to calculating the macroblock difference.

It is a further objective of the invention to provide a Frame Difference Unit and method capable of receiving and storing data in different orders.

It is a still further objective of the invention to provide a unit and method for reformatting macroblock data prior to sending the macroblock data to the next unit in the encoder.

SUMMARY OF THE INVENTION

These and other objectives of the invention are achieved by the MPEG2 compliant digital video encoder of the invention. For example, according to the method and apparatus of the invention there is provided a system and method for formatting reference and current macroblock data prior to calculating the macroblock difference. This is accomplished with a Frame Difference Unit capable of receiving and storing data in different orders, as well as in different formats. This results in reformatting macroblock data prior to sending the macroblock data to the next unit in the encoder.

THE FIGURES

The invention may be more clearly understood by reference to the Figures appended hereto.

FIG. 1 shows a flow diagram of a generalized MPEG2 compliant encoder 11, including a discrete cosine transformer 21, a quantizer 23, a variable length coder 25, an inverse quantizer 29, an inverse discrete cosine transformer 31, motion compensation 41, frame memory 42, and motion estimation 43. The data paths include the ith picture input 111, difference data 112, motion vectors 113 the picture output 121, the feedback picture for motion estimation and compensation 131, and the motion compensated picture 101. This FIGURE has the assumptions that the ith pictures exists in Frame Memory or Frame Store 42, and that the i+lth picture is being encoded with motion estimation.

FIG. 2 illustrates the I, P, and B pictures, examples of their display and transmission orders, and forward, and backward motion prediction.

FIG. 3 illustrates the search from the motion estimation block in the current frame or picture to the best matching block in subsequent or previous frame or picture. Elements 211 and 211' represent the same location in both pictures.

FIG. 4 illustrates the movement of blocks in accordance with the motion vectors from their position in a previous picture to a new picture, and the previous picture's blocks adjusted after using motion vectors.

FIG. 5 shows the combination of three encoder chips of the invention. These are the Intra-chip or Intra-processor 601, the Reference-chip or Reference-processor 901, also referred to equivalently herein as a Reconstruction-chip or Reconstruction-processor 901, the Search-chip or Search-processor 801, and associated RAM chips 531, 533, and 535, including DRAM chips and SRAM chips. The Intra-chip or Intra-processor contains the host processor interface, it receives digitized filtered video input 541, and it produces a compressed video output 543.

FIG. 6 shows an I-frame video encoder module 601 with a host interface 611, an internal RISC processor 621, an interface to motion estimation means 631, a pixel interface 641 for receiving pixel data from a pixel bus 643, a frame memory interface 651 receiving frame data from and sending frame data to an external RAM 653, a Discrete Cosine Transform (DCT) processor 671, a quantization unit 673, a variable length encoder 675, a FIFO buffer 677, and a compressed store interface 679.

FIG. 7 shows a frame memory map 701, with processor private storage 711 and five memory segments 721, 723, 725, 727, and 729.

FIG. 8 shows an S chip or processor 801, with a search memory interface, an Search-input buffer 821, Search-motion estimation 803, and an X-chip interface 831.

FIG. 9 shows an Reference-chip or processor 901 with a reference memory interface 911, an Reference-input buffer 921, Reference-motion estimation 903, an IR chip or processor interface 931, an Reference-chip or processor element 901', inverse quantization (IQ) 941, an inverse discrete cosine transform unit (IDCT) 943, and error prediction and motion compensation 945.

FIG. 10 shows the organization of the luminance and chrominance words to be concentrated and the element GRAM.

FIG. 11 shows the predicted error array with luminance data.

FIG. 12 shows the predicted error array with chrominance data.

DETAILED DESCRIPTION OF THE INVENTION

The invention relates to scalable MPEG and HDTV compliant encoders and encoding processes especially the processing of current and reference macroblock data. The encoding functions performed by the encoder include data input, spatial compression, motion estimation, macroblock type generation, data reconstruction, entropy coding, and data output. Spatial compression includes discrete cosine transformation (DCT), quantization, and entropy encoding. Temporal compression includes intensive reconstructive processing, such as inverse discrete cosine transformation, inverse quantization, and motion compensation. Motion estimation and compensation are the temporal compression functions. Spatial and temporal compression are repetitive functions with high computational requirements.

More particularly the invention relates to a processor for performing spatial and temporal compression including discrete cosine transformation, quanton, and prediction, and even more particularly to a system for accomplishing spatial and temporal compression.

The processor system of the invention has an I-frame only video encoder module with a Discrete Cosine Transform processor, a quantization unit, a variable length encoder, a FIFO buffer, and a compressed store interface. The system also includes a second processor element, that is, a R-processor or Reconstruction processor with a reference memory interface, motion estimation and compensation capability, inverse quantization, and inverse discrete cosine transformation, and motion compensation means; and at least one third processor element motion estimation. The system can be in the form of a single integrated circuit chip, or a plurality of integrated circuit chips, that is one for each processor, the I-frame video encoder module, the second processor element, and the third processor element. There can be one or more of the third processor units.

The first compression step is the elimination of spatial redundancy, for example, the elimination of spatial redundancy in a still picture of an "I" frame picture. Spatial redundancy is the redundancy within a picture. Because of the block based nature of the motion compensation process, described below, it was desirable for the MPEG-2 Standard to use a block based method of reducing spatial redundancy. The method of choice is the Discrete Cosine Transformation, and Discrete Cosine Transform coding of the picture. Discrete Cosine Transform coding is combined with weighted scalar quantization and run length coding to achieve still further levels of compression.

The Discrete Cosine Transformation is an orthogonal transformation. Orthogonal transformations, because they have a frequency domain interpretation, are filter bank oriented. The Discrete Cosine Transformation is also localized. That is, the encoding process samples on an 8×8 spatial window which is sufficient to compute 64 transform coefficients or sub-bands.

Another advantage of the Discrete Cosine Transformation is that fast encoding and decoding algorithms are available. Additionally, the sub-band decomposition of the Discrete Cosine Transformation is sufficiently well behaved to allow effective use of psychovisual criteria.

After transformation, many of the frequency coefficients are zero, especially the coefficients for high spatial frequencies. These coefficients are organized into a zig-zag pattern, and converted into run-amplitude (run-level) pairs. Each pair indicates the number of zero coefficients and the amplitude of the non-zero coefficient. This is coded in a Variable Length Code.

Motion compensation is used to reduce or even eliminate redundancy between pictures. Motion compensation exploits temporal redundancy by dividing the current picture into blocks, for example, macroblocks, and then searching in previously transmitted pictures for a nearby block with similar content. Only the difference between the current block pels and the predicted block pels extracted from the reference picture is actually compressed for transmission and thereafter transmitted.

The simplest method of motion compensation and prediction is to record the luminance and chrominance, i.e., intensity and color, of every pixel in an "I" picture, then record changes of luminance and chrominance, i.e., intensity and color for every specific pixel in the subsequent picture. However, this is uneconomical in transmission medium bandwidth, memory, processor capacity, and processing time because objects move between pictures, that is, pixel contents move from one location in one picture to a different location in a subsequent picture. A more advanced idea is to use a previous or subsequent picture to predict where a block of pixels will be in a subsequent or previous picture or pictures, for example, with motion vectors, and to write the result as "predicted pictures" or "P" pictures. More particularly, this involves making a best estimate or prediction of where the pixels or macroblocks of pixels of the i^(th) picture will be in the i-1^(th) or i+1^(th) picture. It is one step further to use both subsequent and previous pictures to predict where a block of pixels will be in an intermediate or "B" picture.

To be noted is that the picture encoding order and the picture transmission order do not necessarily match the picture display order. See FIG. 2. For I-P-B systems the input picture transmission order is different from the encoding order, and the input pictures must be temporarily stored until used for encoding. A buffer stores this input until it is used.

For purposes of illustration, a generalized flow chart of MPEG compliant encoding is shown in FIG. 1. In the flow chart the images of the i^(th) picture and the i+1^(th) picture are processed to generate motion vectors. The motion vectors predict where a macroblock of pixels will be in a prior and/or subsequent picture. The use of the motion vectors instead of full images is a key aspect of temporal compression in the MPEG and HDTV standards. As shown in FIG. 1 the motion vectors, once generated, are used for the translation of the macroblocks of pixels, from the i^(th) picture to the i+1^(th) picture.

As shown in FIG. 1, in the encoding process, the images of the i^(th) picture and the i+1^(th) picture are processed in the encoder 11 to generate motion vectors which are the form in which, for example, the i+1^(th) and subsequent pictures are encoded and transmitted. An input image 111× of a subsequent picture goes to the Motion Estimation unit 43 of the encoder. Motion vectors 113 are formed as the output of the Motion Estimation unit 43. These vectors are used by the Motion Compensation Unit 41 to retrieve macroblock data from previous and/or future pictures, referred to as "reference" data, for output by this unit. One output of the Motion Compensation Unit 41 is negatively summed with the output from the Motion Estimation unit 43 and goes to the input of the Discrete Cosine Transformer 21. The output of the Discrete Cosine Transformer 21 is quantized in a Quantizer 23. The output of the Quantizer 23 is split into two outputs, 121 and 131; one output 121 goes to a downstream element 25 for further compression and processing before transmission, such as to a run length encoder; the other output 131 goes through reconstruction of the encoded macroblock of pixels for storage in Frame Memory 42. In the encoder shown for purposes of illustration, this second output 131 goes through an inverse quantization 29 and an inverse discrete cosine transform 31 to return a lossy version of the difference macroblock. This data is summed with the output of the Motion Compensation unit 41 and returns a lossy version of the original picture to the Frame Memory 42.

As shown in FIG. 2, there are three types of pictures. There are "Intra pictures" or "I" pictures which are encoded and transmitted whole, and do not require motion vectors to be defined. These "I" pictures serve as a source of motion vectors. There are "Predicted pictures" or "P" pictures which are formed by motion vectors from a previous picture and can serve as a source of motion vectors for further pictures. Finally, there are "Bidirectional pictures" or "B" pictures which are formed by motion vectors from two other pictures, one past and one future, and can not serve as a source of motion vectors. Motion vectors are generated from "I" and "P" pictures, and are used to form "P" and "B" pictures.

One method by which motion estimation is carried out, shown in FIG. 3, is by a search from a macroblock 211 of an i^(th) picture throughout a region of the next picture to find the best match macroblock 213. Translating the macroblocks in this way yields a pattern of macroblocks for the i+1^(th) picture, as shown in FIG. 4. In this way the i^(th) picture is changed a small amount, e.g., by motion vectors and difference data, to generate the i+1^(th) picture. What is encoded are the motion vectors and difference data, and not the i+1^(th) picture itself. Motion vectors translate position of an image from picture to picture, while difference data carries changes in chrominance, luminance, and saturation, that is, changes in shading and illumination.

Returning to FIG. 3, we look for a good match by starting from the same location in the i^(th) picture as in the i+1^(th) picture. A search window is created in the i^(th) picture. We search for a best match within this search window. Once found, the best match motion vectors for the macroblock are coded. The coding of the best match macroblock includes a motion vector, that is, how many pixels in the y direction and how many pixels in the x direction is the best match displaced in the next picture. Also encoded is difference data, also referred to as the "prediction error", which is the difference in chrominance and luminance between the current macroblock and the best match reference macroblock.

The operational functions of an MPEG2 encoder are implemented in three basic devices: an I or Intra device, an R or Reconstruction or Reference device, and an S or Search device. The functions are partitioned according to application needs, silicon size, tools and design complexity, and performance.

As shown in FIG. 6 all external communications including pixel interface 641, host interface 611, and output data interface 679 are done in a single I device 601. The I device 601 is the master interface of the encoder, and is a basic requirement in any video compression application using the chip set of the invention, as shown in FIG. 5. A programmable processor 621 along with the entropy coding functions, that is the Discrete Cosine Transform processor unit 671, the quantization unit 673, and the variable length encoder unit 675, are incorporated in this chip. As a result, this device could be used in an application requiring encoding of I-only pictures. A reconstructed interface is also added to allow functional expansions. The processing functions applied prior to encoding are also included in this device.

Reconstructive processing of the macroblock is needed for all non I-picture coding, that is P picture and B picture encoding. Functions such as Inverse Discrete Cosine Transformation 943 (IDCT), Inverse Quantization 941 (IQ), and Motion Compensation 903 (MC) are consolidated in a single chip, the R chip or R processor, 901, as shown in FIG. 9. The R chip or R-processor is also referred to as the Reconstruction chip. A small motion estimation function capability with a programmable processor is also added to handle low motion applications. A search result interface is installed for higher motion applications. As a result, the I and R-chips together could be used in applications with less motion such as distance learning, video conferencing, surveillance, etc.

Motion estimation is a repetitive function and has high computational requirements. A hardware device, the Search-chip or processor 801 shown in FIG. 8 with external programmable registers is dedicated to this function. An expansion interface is installed to attain a larger search range. The three chip configuration can be used for applications like broadcast transmission, and the like. For higher motion, such as high speed photographic scientific applications, additional S chips 801 provide higher picture quality with a larger search range. This is a scalable feature of the architecture.

Chip Partition

The connections of the three encoder chips or processor elements is shown in FIG. 5. FIG. 5 shows the combination of three encoder chips or processor elements. These are the Intra-chip or Intra-processor 601, the Reference-chip or Reference-processor 801, the Search-chip or Search-processor 901, and associated RAM chips 531, 533, and 535, including DRAM chips and SRAM chips. The Intra-chip or Intra-processor is the host processor interface, it receives digitized filtered video input 541, and it produces a compressed video output 543.

I-chip or Processor

The I-chip or processor 601, shown in FIG. 6 handles the input data 541 and output bitstream 543 of the encoder system. Incoming pixel data is stored in frame format in an external DRAM, referred to as a frame store. This processor performs the core functions necessary for I frame encoding. Pixel data is converted from the RGB format to the YCbCr format, if needed. Pixel data is monitored for scene changes and for repeat fields created by 3:2 pulldown. Incoming pixel data is also adjusted to create HHR output format. The encoder can receive field or frame input format and output field or frame encoded data, regardless of how it was input. Input 4:2:2 data can be encoded as 4:2:2 or 4:2:0 output. The on-chip RISC processor 621 is responsible for adaptive DCT, adaptive quantization, and rate control. The processor has a dynamically partitionable structure that allows it to operate as a 4 byte engine or four 1 byte engines. This is described in our commonly assigned, U.S. Pat. No. 5,644,504 filed Mar. 27, 1995 by Charles Boice, John M. Kaczmarczyk, Agnes Ngai, and Robert C. Woodard for DYNAMICALLY PARTITIONABLE DIGITAL VIDEO PROCESSOR, the disclosure of which is incorporated herein by reference.

The encoded macroblock is merged with header information as described in our commonly assigned, U.S. Pat. No. 5,526,054, filed Mar. 27, 1995 by James D. Greenfield, Diane M. Mauersberg, and Agnes Ngai, for APPARATUS FOR HEADER GENERATION, the disclosure of which is hereby incorporated herein by reference. This creates the final MPEG-2 or MPEG-1 output bitstream which the encoder can store to an external DRAM or ship to a FIFO, for example, through compressed store interface 679. When the picture is stored to DRAM it can be read out by the user through the host interface in non-real time.

R-chip or Processor

The R chip or processor 901, also referred to as the Refinement chip or the Reconstruction chip, shown in FIG. 9 is responsible for search motion estimation refinement and reconstruction of pictures for motion compensation. External DRAM is used to support the motion estimation function. The R chip or processor functional unit performs all the base functions required for reconstruction of pictures and motion estimation, including calculating and process for the frame differences.

The primary functions of the processor are macroblock type decisions, adjusting search range per picture, and motion estimation assists. Both quantizer data and Search chip search results are received through a common chip interface. Quantized data is then dequantized using up to four matrix tables. The IDCT converts the coefficients to pixel data via a two dimensional inverse transform. This reconstructed picture data is saved as reference data by the memory interface for subsequent picture coding. The motion estimation can support field, frame dual prime, bidirectional motion types to half pel resolution along with I, P and B pictures.

The two chip configuration (Intra- & Refinement/Reconstruction- chips) can support up to +/-8H and +/-7V search range and the 3 chip configuration (Intra-, Refinement/Reconstruction, & Search chips) can support up to +/-64H and +/-56V. As motion estimation results are needed, the search window size and best match results are determined, and frame difference data is generated.

Search-chip or Processor

The Search-chip or processor 801, shown in FIG. 8 is responsible for the bulk of the motion estimation. The purpose of motion estimation is to find the location of a macroblock from the current picture (current picture macroblock or "CMB") in the reference picture. This location is determined by finding the best match, which is determined by comparing the CMB data to the reference pictures data and factoring in a bias which is based on the motion of previous pictures.

The entire reference picture cannot be searched in real time. Therefore, a subset of the reference picture is searched. This subset is called the Search Window. See FIG. 3. The larger the search window, the higher the chance of finding an exact match for the CMB. The search window can be significantly increased by employing additional Search-chips 801. Effective motion estimation produces higher quality video and highly compressed bit streams. The Search-processor receives the search window parameters from the processor on the Refinement/Reconstruction-processor and receives luminance picture data in either frame or field format from the Intra-chip, based on the picture structure.

The reference pictures are stored in off-chip SRAM in frame format. The motion estimation unit performs field searches on the CMB and the reference picture. Four field results are calculated along with a frame result for frame structured pictures. The results are in the form of difference data and are biased based on previous pictures motion characteristics. The biased difference data along with motion vectors are sent to the R-chip 901 or processor, e.g., for calculation of the frame difference in the Frame Difference unit.

Processing flow

The I-chip or processor 601 contains both the pre-processing and entropy coding functions. The pre-processing functions are performed prior to any coding functions. The entropy coding is the last portion of picture processing. Its block diagram is shown in FIG. 6.

Host interface

A host interface 611 is installed on the Intra-chip 601, and serves as the main control channel between the encoder chip set and its external world. This interface is a generic 16 bit data and 8 bit address RAM-type protocol. Registers defined at this interface include commands, configuration parameters, encoding parameters, initialization data, mailbox, etc. Host commands include start encode, stop encode, retrieve compressed picture from output DRAM, etc. Configuration parameters include memory size, memory type, number of chips installed in the encoder system, etc.

Encoding parameters can be set at power on or can be modified at a picture boundary to guide the encoding process. These parameters include video input format versus video output format, users matrix tables, intra VLC table, ZZ scan pattern, field/frame picture coding, number of pictures in a sequence, number of pictures in a GOP, number of B pictures, number of reference fields, and user specific data, among others. This interface is also used to initialize the chip set. There are two internal processors in the encoder chip set. Both processors' instructions are downloaded through this interface. In addition there are buffers that require specific contents in order to function properly are also initialized via this interface.

Mailbox is a communication mechanism between the on-chip processor and external processor. When a command or new information is sent to the on-chip processor via the mailbox register, with the correct level of processor code, the new command is implemented. These registers provide flexibility. The defined functions could be selected or de-selected during the coding process by host writes. A stack is also installed at this interface to allow register changes during coding process. The stack is twelve deep. Host writes will only be written into the stack if the encoder is busy in a picture encoding. Information written into the stack will be processed at the end of current picture processing. The encoder appears busy to the external processor until the stack is empty. This design reduces the communication time between picture processings and allows maximum coding time.

Pixel interface

The pixel interface is a 24 bit pixel interface that is used to receive RGB digital input. It can also handle 16 or 24 bit YCbCr input data. A color conversion circuitry, scene change detection logic, and 3/2 pulldown inversion functions are also installed at this interface.

The color conversion, a form of data reduction, is ready to convert the input data to 4:2:2 or 4:2:0 chrominance encoding format.

Every location in a picture is represented by luminance and chrominance pixel data. As specified in the MPEG2 standard, YCbCr data is the input data format for compression and output of decompression. For RGB input data, the input must first be converted into 4:2:2 format prior to any encoding process. If the input data is in 4:2:2 YCbCr format, this means every location in a picture is represented by 8 bits of luminance data and 8 bits of alternative color Cb and Cr data. If the input is in 4:2:0 YCbCr format, this means every location in a picture is presented by 8 bits of luminance data and horizontally and vertically subsampled color Cb and Cr data. The unnecessary and redundant information is removed by the color conversion process and/or 4:2:2 to 4:2:0 decimation at the input stage to achieve one step of compression and to minimize the amount of data flowing through the remaining encoder. This reduces the performance requirement in the remaining devices.

To cover a wide range of applications, MPEG2 standard documents many coding tools and options for the compression process. However, the trade-offs between quality/performance versus complexity for a given application is left for the encoder developers. Many of the coding options are adaptive within a picture, either at the picture level or at the macroblock level. This flexibility allows increased bitrate controls. Dynamic and adaptive changes of coding options could be applied to future coding based on the present information or it could also be applied to present data based on future information. Scene change detection, a look-ahead mechanism that collects picture information prior to the encoding process, provides much more efficient control. Scene change detection indicates large variances between pictures and also complexity differences. The scene change detection calculation is performed on the input data; there are no extra data flows or bandwidth requirements on the remaining functions. Since the input picture order is different from the encoding order, up to three pictures of information are pre-processed, through the scene change detection logic. The scene change detection logic can be used to regulate the quality of the picture being processed. This level of look ahead allows the encoder to dynamically change coding options at both the beginning and the middle of picture processing.

If a 3/2 pulldown inversion is enabled, the input data contains redundant or repeat fields. To be more efficient, the redundant data must be removed prior to encoding. Repeat field detection requires at least one field data be saved. The on-chip storage space requirement for repeat field detection makes it more economical to save the field data in external memory. The input data is first saved in frame store DRAM and has to be retrieved for repeat field detection and picture encoding. The detection scheme is based on a 3/2 pattern. With effective 3/2 PDI logic, for every thirty input pictures, only twenty-four pictures would be encoded after the 3/2 pulldown inversion is applied. The remaining memory bandwidth could then be used for repeat field data fetch. To minimize memory traffic, the following scheme is used: if the input data is odd field first, then the detection is performed on odd field data first, and even field data detection will be performed after a repeat odd field is detected. If the input data is even field first, then the reverse takes place. As a byte of data is received at the pixel interface, the same byte location in the previous field of the same parity is retrieved from frame store memory. A repeat field is determined at the end of field picture input. If the field is a repeat field, then its memory location will be used for input of the next field of the same parity. This eliminates memory fetch complexity during picture encoding.

Frame memory interface

The frame memory interface is shown in FIG. 7. At the output of the pixel interface, the input data is ready to be stored into an external DRAM attached to the Intra-chip, frame memory. This frame memory is only used to save the input picture (current data) until it is ready for encoding. Traffic at this interface is roughly two times the input data transmission rate. A 32 bit data bus is used to support the DRAM, e.g., a 70 ns DRAM. For I and IP coding format, the input picture order is the same as the picture encoding order. For this reason, encoding starts when one macroblock of data is available. In this configuration, the frame memory is divided into six segments, five for input picture data and one for on-chip processor use. A segment of frame memory is selected for each input picture. Data in the picture is stored sequentially as offset of the beginning address as specified by the chosen segment. Each segment is one-quarter of a picture size. Four consecutive segments are used for each input picture. The five segments are used in rotation. The memory partition is shown in FIG. 7.

When the first input picture is received, it is stored into segment 4. Since each segment size is only one-quarter of a picture, the first picture uses segment 4, 3, 2, and 1. The second input picture is stored in segment 0, 4, 3, and 2. The third picture is stored in segment 1, 0, 4, and 3. The fourth picture is stored in segment 2, 1, 0, and 4. The fifth picture uses segment 3, 2, 1, and 0. Then the segment usage repeats again. This scheme allows a minimal memory requirement, 1 MB DRAM, for I and IP configurations. For IPB coding format, the input picture order is different from the encoding order, as shown in FIG. 2. Thus, an input picture must be saved entirely until it is ready to be used. In this case, the memory size is 2 MB for NTSC, and 4 MB for PAL. The frame memory is divided into five segments, four for input picture and one for on-chip processor use. Each segment is equal to the picture size. It is used in similar fashion to the non-IPB format. This scheme allows scalable memory requirements based on the coding formats.

The main traffic of the frame memory is comprised of input data store, 3/2 pulldown inversion data fetch, and encode data fetch. A priority scheme is employed at the frame memory interface with input data store having the highest priority and pulldown inversion data fetch the lowest priority. Input data store is issued when 32B or more data is accumulated in the pixel interface. Data is stored continuously into DRAM, 4 bytes at a time, until there is less than 32B data in the pixel interface, and a pending memory data fetch will then be serviced. The encode data fetch is a 16 by 16 byte macroblock. This fetch is dynamically interruptive at any DRAM row address by an input data store request. The interruptive fetch prevents data overrun at the pixel interface.

Macroblock data is pre-fetched to prevent coding pipeline stall. When the macroblock data is available, the coding process begins. The macroblock data flow depends on the picture type being processed. A predictive picture processing is assumed for the purpose of this description. For a P picture, the current macroblock data is delivered to all three devices simultaneously. The data usage in each chip is different, and the time when the data is used, is also different. The logical flow of this macroblock data, when it is received by all receiving devices, is from the S-chip or processor 801 to the R-chip or processor 901, and then back to the I-chip or processor 501.

Processing in the Search-chip or Processor

Search-input buffer

In the Search-chip 801, shown in FIG. 8 the current macroblock data is primarily used in motion estimation. Depending on the search format selected by the user, the macroblock data is either downsampled 4 to 1, 2 to 1, or remains as 1 to 1 in the input buffer. A single Search-chip 801 provides the largest search range in the 4 to 1 format, and the least in the 1 to 1 format. The downsampled data in both the 4 to 1 and 2 to 1 format are carried out horizontally. This scheme eliminates the complexity of frame and field motion search with the same downsampled data. The downsampled data is saved in search memory, the external memory attached to the Search-chip, where it is to be used as reference data on the subsequent picture coding process. Input data is used in the motion estimation, and provides a more precise difference between the two picture data. At the same time, the data of the previously encoded reference picture in search memory is fetched for motion estimation. The amount of reference data to be fetched for each macroblock processing depends on the macroblock location and the search range.

S-motion estimation

To conserve chip real estate (silicon area), the on-chip reference data buffers in the motion estimation unit can contain 20 out of the 128 lines in the search window at a time. The reference data is fetched as the search process continues. The reference data buffers are comprised of two equal sized units. One of these units is used for odd line data and the other one is for even line data. The two buffers are separate entities. Thus, odd data search and even data search processes can take place simultaneously.

The biggest challenge in motion estimation is the computational power requirement. To minimize search circuitry, field searches are performed together, and the field search results are combined to form frame searches. For example, let Cf1 be the odd lines of current macroblock data, Cf2 be the even lines of current macroblock data, Rf1 be the odd lines of reference data, and Rf2 be the even lines of reference data.

Four field searches, Cf1 versus Rf1, Cf1 versus Rf2, Cf2 versus Rf1, and Cf2 versus Rf2 are performed concurrently. The results of Cf1 versus Rf1 and Cf2 versus Rf2, and Cf2 versus Rf1 and Cf1 versus Rf2 are combined to form the frame search results. The scheme eliminates the frame search circuitry.

Search-chip or Processor Result

The five full pixel refinement results are generated for each frame structured macroblock, one best match for the current odd field and one best match for the current even field.

Xchip interface

The xchip interface 831 supports communications between the Search-chip or processor 901 and Refinement-chip or Reconstruction-chip or processor 801 as well as among the Search-chips 901 in the configuration. For every macroblock, up to five search results, one frame and four fields, are passed to the R-chip 801 via this interface. This interface is also used for Search-chip 901 to Search-chip 901 communications. For multi-chip configuration, each Search-chip 901 has a chip ID. A pre-defined wiring pattern at each set of Search-chip 901 pins is used as the chip ID or address. Address 0 identifies the Search-chip 901 that has the main communication with the R-chip or processor 801. The encoder structure can support one, two or four Search-chips 901. Address 3 identifies the last Search-chip 901 in the chain. In a four Search-chip 901 configuration, the search window is divided into four quarters. Address 0 handles the upper left quarter, address 1 handles the upper right quarter, address 2 handles the lower left quarter and address 3 handles the lower right quarter. Search-chip 3 forwards the search result to Search-chip 2 when it is available. Similarily, for Search-chip 2 to 1 and Search-chip 1 to 0. The best match result obtained from the higher address Search-chip is compared with the result obtained in the receiving chip. The best of the two is then forwarded to the next Search-chip. The best match from all Search-chips is finally selected and returned to the R-chip.

Processing in R-chip or Processor

R-input buffer

The current macroblock data that was previously received from the Intra-chip 601 and is buffered on this chip, is used in the refinement process.

In IPB mode, the R-chip 801 processing lags the Search-chip 901. To ensure the pipeline is constantly full, the buffer is large enough for two macroblocks of data. The next current macroblock data is fetch when there is space in both the Search-input and R-input buffers.

R-motion estimation

The reference data has previously been saved in the external memory, i.e., reconstructed memory, connected to the R-chip or processor 801, i.e., the Refinement- or Reconstruction-chip. The reference data, as the name implies, is composed of reconstructed data. When this data is used in motion refinement, it produces a prediction difference that matches the one reconstructed by the decoder. This scheme minimizes the difference between compression and decompression processes.

The R-chip or processor 801 also receives the search format selected by the user. Depending on the search format, the search results received from the Search-chip or processor 901 are upscaled accordingly back to the full picture resolution. A search refinement is performed based on the search result, including result from the 1 to 1 format. A maximum refinement search range of +/-4H and +/-1V is used.

Another big challenge of motion estimation is memory bandwidth. The reference data retrieved from reconstructed memory, once per macroblock, is buffered on-chip until the frame difference data is generated. This scheme minimizes external memory traffic. Each search result is first refined on a full pixel boundary. At most three full pixel results continue to the next refinement process, half pixel refinement. Up to eight half pixel macroblocks around each full pixel refinement result can be identified for further half pixel refinement search. All the full and half pixel refinement results are transferred to the on-chip processor, that is, the R-processor.

IR-chip interface

Depending on the search type, the R-processor 801 determines the macroblock type and the motion vector for every macroblock processed. Selectable search types may include frame only, field only, full pixel only, half pixel only, and adaptive field/frame motion. If adaptive frame/field motion estimation is selected, the best matched macroblock is used to continue the coding process. Based on the best matched decision, the matching chrominance data is retrieved from reconstructed memory. Both the luminance and chrominance frame difference data are generated and buffered in the Intra-chip 601 and R-chip 801 interface. The luminance difference data is transferred to the Intra-chip 601 first. When the quantized luminance data is returned to the R-chip 801, the chrominance difference data is then transferred to the Intra-chip 601. Both the difference data and the quantized data share the same bi-directional data bus between the Intra-chip 601 and R-chip 801. The data transfers are staged to avoid bus collision.

The quantized data is first passed through the inverse quantizer 941, then the inverse DCT unit 943, and then finally the motion compensation unit 945. The IDCT data is added to the current macroblock data, the one used in the macroblock search, as motion adjust in the Motion Compensation (MC) unit 945. The MC unit 945 produces the reconstructed data. It is buffered and ready to be stored into the reconstructed memory and be used as refinement reference data for subsequent picture coding.

In IP coding format the search refinement circuits on the R-chip or processor 801 are used as a small motion estimator. The center of the search window is the location of the current macroblock. The R chip 801 can support up to +/-8H and +/-7V search ranges in the IP mode. Similarly to the IPB coding format, the reference data is fetched once per macroblock. This data is buffered on-chip until the frame difference data is created. A motion estimation on full pel is first performed. A refinement search is then performed on the best matched full pel macroblock data. Two refinements are carried out, dual prime and half pel search.

A best matched full pel macroblock data is split into odd and even field data. For each field data, the opposite parity data, with +/-1 delta, is retrieved from external memory by extending the origin field data address as specified in the standard. The field data is interpolated with its associated opposite parity data to form the reference data to be used in dual prime motion estimation.

Half pel refinement is performed by a process similar to the process used in IPB coding. All results including full pel, dual prime, and half pel searches are collected by the R-processor. The remaining processes are similar to the IPB mode.

Reference memory interface

For every macroblock process, there is a reference data fetch, a dual prime data fetch, a best matched chrominance data fetch, a reconstructed luminance data store, and a reconstructed chrominace data store. To reduce the memory bandwidth requirement, the reference data is only fetched once per macroblock. To ensure the pipeline is consistently full, the memory operations are handled in a specific order per the macroblock location in the picture. Since motion estimation is performed on just the luminance data, to improve the memory read rate for a specific operation, the luminance and chrominance data are stored in different regions in reconstructed memory.

Frame Difference Unit

A further aspect of the Reconstruction or R-Chip or processor 801 is the Frame Difference Unit (FD). The Frame Difference Unit calculates the difference, that is the difference in luminance and chrominance, between the current macroblock and the best match reference macroblock. Data, that is reference macroblock chrominance and luminance data and current macroblock chrominance and luminance data, to be processed through the Frame Difference Unit arrives in various word lengths and must be formatted such that when used it has the same format as other source data that is used. Data may be stored to and retrieved from memory in two different orders, depending on controls within the Frame Difference Unit. The data also needs to be reformatted prior to sending it to the next unit in the Encoder. These various word lengths and formatting requirements impose difficulties in designing addressing for storage arrays within the Frame Difference Unit.

The inputs to the Frame Difference Unit are the current macroblock and reference macroblock luminance and chrominance data. The output of the Frame Difference Unit is the Predicted Error, that is, the chrominance and luminance difference data.

The Luminance data comes from the dual prime unit on the R- or Reconstruction-chip or processor 801, with the current macroblock Luminance data and the reference macroblock Luminance data coming from the dual prime unit on the chip. The two luminance data are subtracted to obtain the difference or predicted error for the luminance. This difference is stored in an array for transmission to the Intra-processor or chip at the appropriate time.

The current macroblock chrominance data is received from the I-chip or Intra-processor 601 and is stored in an array for later processing. The reference macroblock chrominance data is received from memory associated with the Reconstruction-chip or Reconstruction-processor 801 and stored in another array for later processing.

The current macroblock chrominance data and the reference macroblock chrominance data are subtracted and the difference thereof is then stored in another segment of the same array that the luminance reference data was stored in. The chrominance difference data will also be sent out to the Intra-chip or Intra-processor 801 at a proper time after transmission of the Luminance difference data.

The luminance difference result is 18 bits wide and is to be written to the result GRAM which is 36 bits wide. Depending on a control line this data is to be written to sequential addresses within GRAM or to every other 4 addresses (that is, 4 addresses, skip 4 addresses, 4 addresses, skip 4 addresses, etc.) until the buffer is full. As used herein, every other 4" means the addressing scheme described hereinabove.

The data is to be written as WORD1 concatenated with WORD2 across each line as addressed in the GRAM.

The luminance predicted error (that is, the output of the result GRAM for luminance) is sent to the Intra-chip or Intra-processor 601 18 bits at a time, alternating between the WORD1 half of the GRAM and the WORD2 half of the GRAM until all of the Luminance words are sent. This is illustrated in FIGS. 10 and 11.

The current chrominance reference data from memory is received in 32 bit words and is to be written 32 bits at a time to the reference array. For a chroma format of 4:2:0 the array will be only half filled. Writes to this array are always addressed sequentially, and the reads can either be sequential or addressed every other 4 lines. Data is to be read out 32 bits at a time. For a 4:2:0 chroma format, the array needs to be only half read.

The chrominance data from the Intra-chip or Intra-processor 601 is received a byte at a time and written a byte at a time to the current array. The data bytes are to be written as 4 bytes across each line of the array. For a chroma format of 4:2:0, this array will be only half filled. Writes to this array are always addressed sequentially, and reads can be either sequential or addressed every other 4 lines. Data is to be read out 32 bits at a time. For a 4:2:0 chroma format the data needs to be only half-read.

The chrominance difference result is 36 bits wide and is to be written to the result GRAM which is 36 bits wide, as shown in FIG. 10. Depending on a control line this data is to be written to sequential addresses within that GRAM or to every other 4 addresses until the buffer is full. The data is to be written as one 36 bit word across each line as addresses in the GRAM.

The chrominance predicted error, that is, the output of the result GRAM for chrominance, is to be sent to the Intra-chip or Intra-processor 18 bits at a time, using selectable combinations of U1, U2, U3, U4, V1, V2, V3, or V4, for the amount of data that was stored for either of the chroma formats 4:2:0 or 4:2:2.

For sequential addressing, for nn bits where one full line is to be written for each write, a k bit counter needs to be implemented, where

    nn=2.sup.k.

For example, where the reference array needed to have 64 entries, a six bit counter would be used, with bits 0,1,2,3,4,5.

The counter address will then map directly to the sequential address, that is

    sequential.sub.-- addr(0 to 5)=counter(0 to 5).

To design the addressing structure that provides the addresses that sequence through 4 addresses, then skips 4, then 4 addresses, and so on, the counter used in the sequential case can be used and the bits remapped, so that

    every.sub.--other.sub.-- 4.sub.-- addr=counter(1 to 3,0,4,5).

Now, to design a sequential addressing structure where there will be p accesses per line for each line of the array, in an array of nn lines

    nn×p=2.sup.k.

For example, where the current data array needed to have 64 lines, with 4 accesses per line, an 8 bit counter is needed to address 256 entries, that is, bits 0 to 7.

The most significant 6 bits of the counter address is then used to produce an address that accesses each line four times in a row. That is

    sequential.sub.-- addr(0 to 5)=counter(0 to 5)

where bits 6 and 7 are not used.

To design the addressing for the luminance section of the predicted error array, where there are 64 lines of two words each, or 128 entries, a 7 bit counter is used. To achieve 2 writes per line, all but the last bit of the counter address is used, that is,

    2.sub.-- write.sub.-- addr(0 to 5)=counter (0 to 5)

where bit 6 is not used.

For the sequential case, the 2₋₋ write₋₋ addr is used as:

    lum.sub.-- seq.sub.-- addr(0 to 5)=2.sub.-- write.sub.-- addr(0 to 5).

For the every other 4 case the 2₋₋ write₋₋ addr bits are remapped to yield the lum₋₋ leo4₋₋ addr is

    lum.sub.-- eo4.sub.-- addr(0 to 5)=2.sub.-- write.sub.-- addr(1 to 3, 0, 4, 5).

To design the write addressing for the chrominance section of the predicted error array, where there are 64 lines and each line is 36 bits wide, a 7 bit counter is used. To achieve 1 write per line, all but the first bit of the counter address is used:

    1.sub.-- write.sub.-- addr(0 to 5)=counter(1 to 6)

where bit 0 is not used. This is illustrated in FIG. 12.

For the sequential case, the 1₋₋ write₋₋ addr is used:

    chr.sub.-- seq.sub.-- addr(0 to 5)=1.sub.-- write.sub.-- addr(0 to 5).

For the every other 4 case, the counter address bits were remapped to produce the chr₋₋ eo4₋₋ addr is used:

    chr.sub.-- eo4.sub.-- addr(0 to 5)=counter(2 to 4,1,5,6,).

To design the read addressing for the chrominance section of the predicted error array, where there are 64 lines where each line is 36 bits each, a 7 bit counter is used. The chrominance has to be read according to a frame or a field indicator, where:

for frame mode:

referring to figure for chrominance:

read u1 and u3 bytes;

read v1 and v3 bytes;

read u2 and u4 bytes;

read v2 and v4 bytes.

To do this, bit 1 of the counter is not used in order to generate the proper sequence of addresses:

    frame.sub.--read.sub.-- addr(0 to 5)=counter (0, 2 to 6),

where bit 1 is not used.

And likewise for the field mode,

for field mode:

referring to figure for chrominance;

read u1(odd) and u3(odd) bytes;

read v1(odd) and v3(odd) bytes;

read u2(odd) and u4(odd) bytes;

read v2(odd) and v4(odd) bytes;

read u1(even) and u3(even) bytes;

read v1(even) and v3(even) bytes;

read u2(even) and u4(even) bytes;

read v2(even) and v4(even) bytes.

Odd refers to lines 0 to 3, 8 to 11, 16 to 19, etc. Even refers to lines 4 to 7, 12 to 15, 20 to 23, etc. To accomplish this the counter address is remapped to provide the proper sequence of addresses:

    field.sub.-- read.sub.-- addr(0 to 5)=counter (2 to 4, 0, 5 to 6)

Entropy Processing in Intra-chip

Intra-processor

The Intra-processor 601 is shown in detail in FIG. 6. When the current macroblock data is made available from frame memory, the energy content of the macroblock, which is used to determine a quantization level for the best rate control, is calculated by the I-processor 601. A frame or field DCT decision is made by the I-processor 601 on the frame difference data when it is returned from the R-chip 801. The Intra-processor 601 has a dynamically partitionable feature that allows it to operate as four 1 byte units or as one 4 byte entity. Both the quantization and field/frame DCT calculations are performed in partitioned mode which provides a four fold performance gain.

Depending on the input picture and the specified output bitrate, overflow or underflow conditions may occur. It is the rate control's responsibility to avoid either of these conditions. Use of DC only and external FIFO feedback are installed to avoid the overflow case. Padding is put in place to control or even eliminate the underflow case.

Picture coding time depends on the input format and coding format. Picture rate is specified by the application. Picture gap is the time the encoder is not busy in picture coding. Picture gap is determined by picture rate and picture coding time. Padding, if needed, is performed in picture gap. This limits the maximum bits the encoder can pad per gap. The encoder keeps track of the number of bits generated per picture and bits allocated per picture. If the bits generated is less than bits allocated, padding will be used to fill the unused bits. The unused bits from a picture may be padded across several picture gaps. This mechanism ensures the bitstream complies with the application without performance violation.

Quantizer

A coefficient clipping feature is present in the quantizer unit. The coefficient clipping register, written by microcode, is used to contain the position of the last non-zero amplitude coefficient in a block. When the rate control detects a near overflow condition, the code can write a value into the coefficient clipping register. This value is calculated based on overflow closeness. All coefficients after the location specified in the coefficient clipping register are made zero. This scheme is also used to produce a constrained bitstream. A constrained bitstream is defined in the MPEG2 Main Profile at Main Level standard as all macroblocks in a slice, except two macroblocks, must contain less than 4608 bits each. The encoder keeps track of the bits generated per macroblock and the number of macroblocks in a slice that have over 4608 bits. When two macroblocks having over 4600 bits are encountered, the coefficient clipping register is set to 31 for the remaining of the slice. In this case, the chip will use the first 31 coefficients to form the bitstream. The number of bits used per coefficient depends on the coefficient value. Twenty-four bits are used to code a maximum value. Assuming all 31 coefficients contain the maximum number, 4464 bits will be produced per macroblock in 4:2:0 format. This mechanism ensures that the output bitstream is constrained and also curbs the bits generated to avoid overflows.

Variable Length Encoder

The output of quantization, prior to ZZ scan processing, is returned to R-chip 801 for reconstruction of the picture. This eliminates some design complexity and an inverse ZZ function is not required on the R-chip 801. The scan format is selectable at the host interface. Microcode can also select the scan format based on picture format. Alternate scan is used for interlaced coding and traditional scan for progressive pictures.

ZZ scan is applied to the quantized data, which is variable length coded with the Huffman table. The variable length data is saved in a buffer. Coded block pattern, as defined in the MPEG2 standard, is used to indicate which block contains non zero data in the macroblock. When all blocks are coded, headers are attached to the VLC data.

Compressed store interface

Headers are generated in a flexible manner. The header definitions are stored in a programmable table. The microcode also has the capability to modify the content of the header table when changes occur in the standard. Depending on the application needs, the microcode selects which header to generate. The elementary stream is found from the coefficient data along with the headers.

Integrated System

In one embodiment there is provided according to our invention an MPEG2 compliant digital video encoder system having an I-frame video encoder module 601 with (1) a host interface 611, (2) a pixel interface 641 for receiving pixel data from a pixel bus 643, (3) a frame memory interface 651 for receiving and sending frame data, (4) a Discrete Cosine Transform processor 671, (5) a quantization unit 673, (6) a variable length encoder 675, (7) a FIFO buffer 677, and (8) a compressed store interface 679, for generating an I-frame containing bitstream.

In a further exemplification the scalable architecture MPEG2 compliant digital video encoder system the I-frame video encoder module includes (9) an interface to motion estimation means, and the system further includes a second processor, i.e., an R-processor element 901 with (10) a reference memory interface 911, (11) motion estimation means 903, (12) inverse quantization means 941, (13) inverse discrete cosine transform means 943, and motion compensation means 945. The system also includes at least one third processor element or Search processor element 801 with (14) a search memory interface and (15) motion estimation means 801. This embodiment provides an I-P-B datastream.

The encoder can be in the form of a single chip or a plurality of chips. For example, there may be separate integrated circuit chips for the I-frame video encoder module, the second processor element 901, and the third processor element 801. There may also be more then one such third processor element 801.

According to an alternative embodiment of our invention there is provided a digital video encoder system where the I-frame video encoder module 601 includes (9) an interface to motion estimation means, and the system further includes only a second or R-processor element with (10) a reference memory interface 911, (11) motion estimation means 903, (12) inverse quantization means 941, (13) inverse discrete cosine transform means 943, and motion compensation means 945. This embodiment is useful for generating an I-P datastream.

While the invention has been described with respect to certain preferred embodiments and exemplifications, it is not intended to limit the scope of the invention thereby, but solely by the claims appended hereto. 

We claim:
 1. A digital video encoder system having:a. an I-frame only video encoder module for generating an I-frame containing bit stream, said module having a host interface, a pixel interface for receiving pixel data from a pixel bus, a frame memory interface for receiving and sending frame data, a Discrete Cosine Transform processor, a quantization unit, a variable length encoder, a FIFO buffer, and a compressed store interface; and b. a second module for generating I-frame, B-frame, and P-frame containing bit streams, second said module having a reference memory interface, motion estimation and compensation means, inverse quantization, and inverse discrete cosine transformation means for inverting a picture for said motion estimation and compensation means, and further including a frame difference unit having a bit blockable 7 bit address counter for addressing memory addresses for each picture at (1) every address; (2) every other 4 addresses by every₋₋ other₋₋ 4₋₋ addr=counter (1 to 3, 0, 4, 5); (3) each line 4 times in a row by sequential₋₋ addr(0 to 5)=counter(0 to 5); or (4) 64 lines of two words each, each line 2 times in a row by 2₋₋ write₋₋ addr(0 to 5), respectively=counter (0 to 5). 